Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compilation info #87

Closed
wants to merge 2 commits into from
Closed

Compilation info #87

wants to merge 2 commits into from

Conversation

Kangz
Copy link
Collaborator

@Kangz Kangz commented Apr 21, 2021

PTAL!

Do you think that WGPUCompilationInfo should be extensible so that the WebGPU library can pass more information to the application in the future?

Kangz added 2 commits April 21, 2021 14:14
 - Rename of attachment descriptor types.
 - Rename of attachment descriptors .attachment -> .view
 - Rename of BlendFactors
 - Rename of SetBlendColor to SetBlendConstant
@Kangz Kangz requested review from kvark and toji April 21, 2021 12:17
@kvark
Copy link
Collaborator

kvark commented Apr 21, 2021

Yes, making it extensible sounds reasonable.

@Kangz
Copy link
Collaborator Author

Kangz commented Apr 21, 2021

Also maybe for WGPUCompilationMessage. @toji WDYT?

Copy link

@toji toji left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. And yes, it's probably a decent idea for at least CompilationInfo to be extensible. Feels like making CompilationMessage extensible may just be unnecessary complexity. If worst comes to worst you could always add a parallel array to CompilationInfo to contain additional per-message data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants